Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(ci): include fixtures for all previous forks in eest releases #1053

Merged
merged 3 commits into from
Jan 14, 2025

Conversation

marioevz
Copy link
Member

@marioevz marioevz commented Jan 7, 2025

🗒️ Description

  • All features now do --until instead of --fork, to include filled tests for legacy forks too.
  • The legacy feature is now removed since stable now includes all forks starting from Frontier.
  • Added a comment to encourage not filling only for a single fork on features and include previous forks too.

This issue was raised by some teams who would like to have all tests in the same package for their QA procedures.

🔗 Related Issues

None

✅ Checklist

  • All: Set appropriate labels for the changes.
  • All: Considered squashing commits to improve commit history.
  • All: Added an entry to CHANGELOG.md.
  • All: Considered updating the online docs in the ./docs/ directory.
  • Tests: All converted JSON/YML tests from ethereum/tests have been added to converted-ethereum-tests.txt.
  • Tests: A PR with removal of converted JSON/YML tests from ethereum/tests have been opened.
  • Tests: Included the type and version of evm t8n tool used to locally execute test cases: e.g., ref with commit hash or geth 1.13.1-stable-3f40e65.
  • Tests: Ran mkdocs serve locally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.

@marioevz marioevz added scope:ci Scope: Continuous Integration type:chore Type: Chore labels Jan 7, 2025
@marioevz marioevz requested a review from danceratopz January 7, 2025 16:27
@danceratopz danceratopz changed the title fix(github): Features for legacy forks chore(ci): include fixtures for all previous forks in eest releases Jan 14, 2025
Copy link
Member

@danceratopz danceratopz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense - LGTM!

I added a changelog entry, we shouldn't forget to mention this in the release notes, even if it's not strictly a breaking change.

This will (slightly) impact hive instances upon the next release, so I created a PR for the devnet-5 hive config that would maintain the current behaviour:

@marioevz marioevz merged commit 27534e1 into main Jan 14, 2025
21 checks passed
@marioevz marioevz deleted the fill-for-previous-forks branch January 14, 2025 21:21
skylenet pushed a commit to ethpandaops/pectra-devnets that referenced this pull request Jan 23, 2025
This PR shouldn't change the current behavior as
[pectra-devnet-5@v1.2.0](https://github.com/ethereum/execution-spec-tests/releases/tag/pectra-devnet-5%40v1.2.0)
only contains tests filled for `Prague` and the `CancunToPragueAt15k`
transition.

It does, however, ensure the current behavior is maintained for this
hive instance for upcoming EEST releases that contain tests filled for
previously deployed forks, which will be the case when this PR gets
merged:
- ethereum/execution-spec-tests#1053

Feel free to disregard this PR, as running tests for all forks might be
desirable 😆 here's what the impact would currently be:
- Prague-only: 4062 tests.
- Until Prague: 6525 tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope:ci Scope: Continuous Integration type:chore Type: Chore
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants